-
Notifications
You must be signed in to change notification settings - Fork 515
[hashicorp_vault] Update Hashicorp vault documentation #15833
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Update documentation for the hashicorp_vault integration. This expands the information on the use-cases supported by the integration, and the data collected. It also reformats the set up instructions to make them easier to follow, and adds common troubleshooting issues.
|
Pinging @elastic/integration-experience (Team:Integration-Experience) |
🚀 Benchmarks reportTo see the full report comment with |
Add warning and troubleshooting advice on use of a TCP socket destination, which may result in blocked vault operations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I think we should bump the system tests to use Vault 1.21 (could be a separate PR).
| ### Compatibility | ||
|
|
||
| ## Audit Logs | ||
| This integration has been tested with HashiCorp Vault 1.11 and 1.21. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I would be more comfortable with the 1.21 statement if 1.21 were used throughout the docker-compose.yml file
| image: vault:1.11.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've changed the documentation to state it's compatible with 1.11 only.
(I did try updating the vault image used, but the vault container didn't properly, so that's something that can be done in a separate PR).
aa23bc9 to
8f78b65
Compare
💚 Build Succeeded
History
cc @mjwolf |
Proposed commit message
Update documentation for the hashicorp_vault integration. This expands
the information on the use-cases supported by the integration, and the
data collected. It also reformats the set up instructions to make them
easier to follow, and adds common troubleshooting issues.
Checklist
changelog.ymlfile.- [ ] I have verified that any added dashboard complies with Kibana's Dashboard good practicesAuthor's checklist
I have followed the updated documentation to set up all inputs supported by this integration (audit log, audit TCP, operational log and metrics), and confirmed following the instructions will result in data flowing into Elastic.
Screenshots
Screenshot of documentation as rendered in Kibana:
